Library Security Levels

After you have created your libraries, determine the security levels for each library. The following examples give you an idea of how you can use libraries and security together to help safeguard models:

• The entire modeling team can have access to the development library and read-only access to the test and production libraries. Authorized project leaders can be assigned to move models from the development library to the test library, and then from the test to the production library.
• Models from other libraries (for example, Sales and Accounting) can be merged from their own libraries in the enterprise model. Modelers working on projects in the Sales or Accounting libraries can have read-only access to the enterprise library and full access to their own projects. Assign one person or group to manage integration to the enterprise model.
• Modelers need full access to their own libraries and read-only access to the libraries of others. This type of security enhances production for the following reasons:
  • Everyone can see what everyone else is working on.
  • All models are stored in one location.
  • Permissions can be changed as different collaborations among modelers become necessary.